Resource CapabilityStatement/FHIR Server from package nictiz.fhir.nl.stu3.eafspraak#1.0.6 (63 ms)

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Source

{
  "resourceType" : "CapabilityStatement",
  "url" : "http://nictiz.nl/fhir/CapabilityStatement/eappointment-servercapabilities",
  "version" : "1.0.1",
  "name" : "eAppointmentServer",
  "status" : "active",
  "date" : "2022-09-27",
  "publisher" : "Nictiz",
  "contact" : [
    {
      "name" : "Nictiz",
      "telecom" : [
        {
          "system" : "url",
          "value" : "https://www.nictiz.nl",
          "use" : "work"
        }
      ]
    }
  ],
  "description" : "This CapabilityStatement describes the minimal requirements for a server to fulfill the eAppointment use case described for MedMij. The MedMij use cases can be found here: https://informatiestandaarden.nictiz.nl/wiki/MedMij:Vcurrent_FHIR_IG",
  "purpose" : "This CapabilityStatement is informative in nature and does not represent the minimum or maximum set of capabilities the client or server should support. The aim is to design the CapabilityStatement as complete as possible, however for the exact set of capabilities the implementation guide of the corresponding information standard should be consulted.",
  "copyright" : "CC0",
  "kind" : "requirements",
  "fhirVersion" : "3.0.2",
  "acceptUnknown" : "both",
  "format" : [
    "xml",
    "json"
  ],
  "profile" : [
    {
      "reference" : "http://fhir.nl/fhir/StructureDefinition/nl-core-patient"
    },
    {
      "reference" : "http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner"
    },
    {
      "reference" : "http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole"
    },
    {
      "reference" : "http://fhir.nl/fhir/StructureDefinition/nl-core-organization"
    },
    {
      "reference" : "http://fhir.nl/fhir/StructureDefinition/nl-core-location"
    },
    {
      "reference" : "http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment"
    }
  ],
  "rest" : [
    {
      "mode" : "server",
      "resource" : [
        {
          "type" : "Appointment",
          "interaction" : [
            {
              "code" : "search-type"
            }
          ],
          "searchParam" : [
            {
              "name" : "date",
              "type" : "date"
            }
          ]
        }
      ]
    }
  ],
  "text" : {
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.